Skip to content

Show the recipient and amount on the Accelerate confirmation - #6337

Open
peachbits wants to merge 6 commits into
developfrom
matthew/accelerate-confirmation-details
Open

peachbits wants to merge 6 commits into
developfrom
matthew/accelerate-confirmation-details

Conversation

@peachbits

Copy link
Copy Markdown
Contributor

Requested by Matthew

Description

Asana task

The Accelerate Transaction confirmation showed only the old and new fee. Acceleration rebuilds and re-signs the whole payment, so the confirmation now shows everything the user is authorizing.

  • Each recipient of the replacement gets a Recipient Address row (with a copy button) and a Send Amount row, read from the spendTargets that the plugin's accelerate() returns.
  • Amounts use the display denomination and exchange rate of the asset being sent, in the same format as the fee rows.
  • The instruction text asks the user to review the recipient, amount, and new fee.
  • With a plugin that does not return spendTargets, the new rows are absent and the modal looks as it did before.

Testing

  • src/__tests__/modals/AccelerateTxModal.test.tsx: single recipient (snapshot), several recipients, a token send, and no spend targets.
  • iOS simulator build with the plugin branch installed: before and after screenshots of the modal are in a comment below.

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

EdgeApp/edge-currency-plugins#467 supplies spendTargets. This PR is safe to merge without it; the rows appear once the app picks up a plugin release that includes it.

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

Tested on an iOS simulator (iPhone 17 Pro) only.

@peachbits

Copy link
Copy Markdown
Contributor Author

📸 Accelerate confirmation, before and after (iOS simulator)

before current develop

before current develop

after this branch

after this branch

Captured by the agent's in-app test run (build-and-test).

@j0ntz j0ntz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed at 61c47da (high): nothing blocking. The inline comments carry one warning and three suggestions.

Nit (commit-subject-50): 0a6c46c69 subject is 60 chars. Suggest Show recipient and amount when accelerating (43).

Rejected in curation (1)
  • src/components/modals/AccelerateTxModal.tsx:127: the target's own currency code is ignored when formatting. Rejected: accelerate is UTXO-only and every spend target pays out in the transaction's own asset, which acceleratedTx.tokenId already names.

The Accelerate modal showed only the old and new fee. Acceleration
rebuilds and re-signs the whole payment, so the confirmation should show
everything the user is authorizing.

The modal now lists the recipient address(es) and the send amount, taken
from the `spendTargets` the plugin's `accelerate()` returns, and the text
asks the user to review them along with the new fee. With a plugin that
does not return `spendTargets` the rows are absent.
@peachbits
peachbits force-pushed the matthew/accelerate-confirmation-details branch from 61c47da to f7560ef Compare November 13, 2026 23:29
@peachbits
peachbits force-pushed the matthew/accelerate-confirmation-details branch from f7560ef to aeb839e Compare November 13, 2026 23:41
@peachbits

Copy link
Copy Markdown
Contributor Author

📸 Three recipients: rows scroll, slider stays in place (iOS simulator)

three recipients

three recipients

three recipients scrolled

three recipients scrolled

Captured by the agent's in-app test run (build-and-test).

@peachbits

Copy link
Copy Markdown
Contributor Author

All four inline comments are addressed in fixups. The commit subject is now Show recipient and amount when accelerating.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants